Hey guys,
I am new here so i dont know if this is the correct place to ask this, but i will give it a try anyways.
I have my zabbix setup in a Kubernetes cluster using "Helm Zabbix". Now zabbix works perfectly however one of my most important uses are the Web Scenarios. I have configured all my web scenarios to have a single step (in most cases), and the timeout for that step is 2 min. However i have noticed a trend over the last few months, that the timeout keeps increasing without a noticeable pattern. Even though zabbix should check each web scenario (220 in total) every 2 minutes, most of the time it does not go back to check for 10-15 minutes, sometimes even 20+. This results in inaccurate monitoring logs, therefore i dont have a clear picture of how long for example a web scenario was really out for.
Would appreciate any help i can get.
I am new here so i dont know if this is the correct place to ask this, but i will give it a try anyways.
I have my zabbix setup in a Kubernetes cluster using "Helm Zabbix". Now zabbix works perfectly however one of my most important uses are the Web Scenarios. I have configured all my web scenarios to have a single step (in most cases), and the timeout for that step is 2 min. However i have noticed a trend over the last few months, that the timeout keeps increasing without a noticeable pattern. Even though zabbix should check each web scenario (220 in total) every 2 minutes, most of the time it does not go back to check for 10-15 minutes, sometimes even 20+. This results in inaccurate monitoring logs, therefore i dont have a clear picture of how long for example a web scenario was really out for.
Would appreciate any help i can get.
Comment